Sending e-mail from a hosted system

ABSTRACT

A method includes receiving e-mail input data from a client at a server that is configured to serve a hosted application that includes an e-mail user interface to the client. The e-mail input data is used to generate an e-mail message from a user of the client, where the client is associated with a first domain and the server is associated with a second domain. An e-mail object corresponding to the e-mail message from the user of the client is generated at the server, and the e-mail object is forwarded from the server to the client along with instructions to convert the e-mail object into the e-mail message and to send the e-mail message from the first domain.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119(e) to U.S.Provisional application Ser. No. 60/892,803, filed on Mar. 2, 2007,entitled “Sending E-Mail From a Hosted System,” which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

This description relates hosted systems and, in particular, to sendinge-mail from within a hosted system.

BACKGROUND

In a client-server system, a server can host an application thatprovides a service to a client, and the client can operate theapplication remotely. For example, a website, such as yahoo.com ormsn.com can run applications that provide a financial portfolio trackingservice to remote clients. The clients can connect to the hosted systemthrough a network and operate the system, enter information concerningtheir portfolios and then track the performance of their portfoliosthrough use of the hosted system. Because the application is hosted andrun by the server and data about the users' portfolios is stored on theserver, the client need not install any software or store any data aboutthe portfolios. Moreover, the application can be updated automaticallyby the server, without the client having to take action to installupdated or additional software. From the perspective of the websiteowner, an advantage of providing the hosted application in anapplication service provider (ASP) model, as opposed to providing theapplication through a stand-alone application that is loaded onto andrun by the client, is that the website owner can more easily update theapplication, communicate with the client, and has access to dataprovided by the client. These advantages allow the website owner to knowand understand the user better, so that the application can be tuned forthe user. In addition, because the user must connect to the server toaccess and use the application, the website owner has the opportunity tocommunicate with the user more frequently.

Some hosted applications provided by a server to a client can include anelectronic mail (“e-mail”) application that allows the user of theapplication to send e-mail messages through the hosted application.E-mail messages are composed in the e-mail application and sent from amail server that is associated with the server. For example, if thehosted application is provided by a server associated with the domainSAP.com, the e-mail messages are sent from a mail server that is alsoassociated with the domain SAP.com. A problem with this is that if auser utilizes the e-mail application of the hosted application to sendmalicious or spam e-mails, network security systems and software mayassociate the malicious or spam e-mail with the domain from which theywere sent (i.e., SAP.com) and may take action to quarantine or blacklistthe domain. Therefore, one malicious user or spam sender utilizing thehosted application may cause the e-mail traffic from non-malicious usersof the hosted application or other users associated with the domain tobe limited or blocked. Furthermore, a SPAM filter may identify an e-mailas SPAM if the domain of the listed as the sender's domain does notmatch the domain of the sending mail server. Thus, legitimate e-mailsmay be routed into junk mail when using a hosted solution, if the usersends e-mail from the domain of hosted solution's mail server but theuser's “from” address has a different domain. In addition, if the domainof the hosted application is used to send a sufficiently large number ofe-mails on behalf of its clients, then according to some laws (e.g.,German Law), the provider of this hosted application may be deemed anInternet Service Provider, which may require that the that the providerconform to certain burdensome and/or costly regulations.

SUMMARY

In a first general aspect, a method includes receiving e-mail input datafrom a client at a server that is configured to serve a hostedapplication that includes an e-mail user interface to the client. Thee-mail input data is used to generate an e-mail message from a user ofthe client, where the client is associated with a first domain and theserver is associated with a second domain. An e-mail objectcorresponding to the e-mail message from the user of the client isgenerated at the server, and the e-mail object is forwarded from theserver to the client along with instructions to convert the e-mailobject into the e-mail message and to send the e-mail message from thefirst domain.

Implementations can include one or more of the following features. Forexample, the e-mail input data can be composed with the e-mail userinterface of the hosted application that is served to the client.Generating the e-mail object can include creating an XML representationof the e-mail message from the user of the client. Forwarding the e-mailobject from the server to the client can include sending instructions tothe client to convert the e-mail object into the e-mail message and tosend the e-mail message through a local e-mail client applicationassociated with the first domain and configured to run on the client.The local e-mail client application can be selected from the groupconsisting of Microsoft Outlook and Lotus Notes. The data indicatingthat the client should unpack the e-mail object and send the e-mailmessage through a local e-mail client application can include ascripting language program. A copy of the e-mail message can begenerated at the server and the copy can be stored in a storage deviceon the server for presentation to the user through the e-mail userinterface of the hosted application served to the client.

In another general aspect a method includes accessing an applicationhosted by a server and served to a client, where the applicationincludes an e-mail user interface that is served to the client and runson the client, and where the client is associated with a first domainand the server is associated with a second domain. E-mail input data isreceived from a user of the client, and the e-mail input data is used togenerate an e-mail message from the user, where the e-mail input data iscomposed within the e-mail user interface of a hosted application. Thee-mail input data is sent from the client to the server, and an e-mailobject corresponding to the e-mail message is received from the server.The e-mail object is converted into the e-mail message, and the e-mailmessage is sent from the first domain.

Implementations can include one or more of the following features. Forexample, receiving the e-mail object can include receiving an XMLrepresentation of the e-mail message from the user of the client.Sending the e-mail message can include sending the message through alocal e-mail client application associated with the first domain andconfigured to run on the client. The local e-mail client application canbe selected from the group consisting of Microsoft Outlook and LotusNotes. The e-mail user interface of the application to the user can beprovided through a browser application running on the client. Aconfirmation message can be sent from the client to server to inform theserver that the e-mail message has been sent.

In another general aspect, a server system includes a network interface,a processor, and an e-mail object generating engine. The networkinterface is configured for connecting the server system to a clientsystem, where the client is associated with a first domain and theserver is associated with a second domain. The processor is configuredfor providing a hosted application that is served to the client, wherethe hosted application includes an e-mail user interface within which auser of the client system that can generate e-mail input data forsending an e-mail message from the user. The e-mail object generatingengine is adapted for receiving the e-mail input data from the clientand generating an e-mail object to be sent to the client system alongwith instructions for converting the e-mail object into an e-mailmessage to be sent from the first domain.

Implementations can include one or more of the following features. Forexample, the e-mail object can include an XML representation of thee-mail message from the user of the client. The instructions forconverting the e-mail object into an e-mail message to be sent from thefirst domain can include instructions to the client to send the e-mailmessage through a local e-mail client application associated with thefirst domain and configured to run on the client. The local e-mailclient application can be selected from the group consisting ofMicrosoft Outlook and Lotus Notes. The instructions for converting thee-mail object into an e-mail message to be sent from the first domaincan include a scripting language program. The hosted application can bea customer relations management application. Internet Protocol headerinformation of the sent e-mail message can be associated with the firstdomain.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example client-server system in whichthe server provides the services of a hosted application to the client.

FIG. 2 illustrates screen shots of an e-mail user interface provided bythe hosted application and a user interface of an e-mail programprovided by an e-mail application running on the client.

FIG. 3 is a flowchart illustrating an example method of operating thesystem of FIGS. 1 and 2.

FIG. 4 is a flowchart illustrating an example method of operating thesystems of FIGS. 1 and 2.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an example client-server system 100 inwhich the server 102 provides the services of a hosted application 104to a client 130. The server can include a memory device 106, such as,for example, a hard disk, a random access memory (RAM) or a read onlymemory (ROM) for storing executable instructions, such as in a computerprogram. The instructions can be executed by a processor 108.

In one implementation, the processor 108 can execute a hostedapplication 104 that can provide services to a client user. In oneimplementation, the hosted application 104 can provide a suite ofbusiness services to a client user. For example, the hosted application104 can provide a suite of customer relationship management (“CRM”)services to a user, so that the user can manage interactions with acustomer. The hosted application “CRM On-Demand,” offered by SAP AG, ofWalldorf, Germany, is an example of such a hosted application.

To utilize the services provided by the hosted application 104, a user150 of the client 130 can connect the client 130 to the server 102through a network 120. The network 120 can be a wide area network(“WAN”), such as, for example, the Internet, or a local area network(“LAN”), such as a corporate network. The client 130 can connect to thenetwork 120 though a first network interface controller 132, and theserver can connect to the network though a second network interfacecontroller 110. After connecting the client 130 to the server 102, theuser 150 can require the server to load and run the hosted application104.

Like the server 102, the client 130 can include a memory device 134,such as, for example, a hard disk, a random access memory (RAM) or aread only memory (ROM) for storing executable instructions, such as in acomputer program. The instructions can be executed by a processor 136.When the client 130 is connected to the server 102 and the hostedapplication 104 is running, the client can access the services providedby the hosted application through a hosted application user interface(“UI”) 134 running on the client. The hosted application UI 134 can beprovided, for example, through a browser application, such as, forexample, Microsoft Internet Explorer or Mozilla Firefox. Instructionsfor operating the browser can be stored on the client's memory 134 andexecuted by the client's processor 136. The client 130 can receive inputdata from a user 150 and send the data to the server 102 for processingand/or storage by the hosted application 104. For example, when thehosted application 104 provides CRM On-Demand services to the client130, the user 150 can enter information about customers with whom theuser interacts, sales made to the customers, call center interactionsand personal meetings with the customers, for processing, organization,and storage within the hosted application 104 on the server 102.

In some implementations, the user 150 may utilize the hosted applicationto send e-mail messages. In one implementation, the user can compose ane-mail message within an e-mail user interface 138 by entering emailinput data (e.g., the text of an e-mail message, the subject of themessage, and the e-mail address of the recipient of the message). Thehosted application 104 can receive the e-mail input data from the client130 and instructions to send an e-mail message based on the e-mail inputdata. In response to the e-mail input data and the instructions, thehosted application 104 can send the e-mail message though a mail server112 associated with the server 102. For example, the mail server 112 andthe server 102 can both be associated with the same domain. For example,the mail server 112 and the server 102 can both be associated with thedomain SAP.com when the hosted application is hosted and provided by SAPAG The client 130 can be associated with a different domain, forexample, the domain adcom.com. The mail server 112 can include aprocessor 114 and a memory device 116 for receiving the e-mail messagefrom the server 102 and sending the e-mail message out through a network118 to the intended recipient.

In another implementation, when a user 150 desires to send an e-mailmessage through the hosted application 104 provided by the server 102,the e-mail message can be sent from a mail server 140 having a domainassociated with the client 130. In this implementation, the user 150 cancompose the e-mail message within the e-mail UI 134 of the hostedapplication UI 134, and e-mail input data and instructions to send themessage are forwarded to the server 102. When the hosted application 104receives the e-mail input data and the instructions to send the message,an e-mail object generating engine 105 within the application 104creates an e-mail object and packages the e-mail object in an XMLrepresentation of the e-mail message, but does not send the message fromthe mail server 112 of the domain associated with the server 102.Instead, the hosted application 104 running on the server 102 sends aresponse to the client with the XML-formatted e-mail object andinstructions to the client to unpack the object and send the emailmessage from a mail server 140 having a domain that is associated withthe client 130.

In one implementation, the instructions to unpack the email object canbe contained in scripting language code (e.g., Javascript) that isexecuted by an engine 142 (e.g., a Java engine). Execution of thescripting language code by can make use of the client's applicationprogramming interface (“API”) (via ActiveX control) to create a newemail message within an email client application (e.g., MicrosoftOutlook or Lotus Notes) 144 running on the client 130. In oneimplementation, the email message is created within the “Outbox” of theemail client 144. After the email message is created within the Outboxof the email client 144, the email client forwards the message to themail server 140 associated with the client 130. The mail server 140contains a memory 146 for storing instructions regarding how to send themail message and also includes a processor 148 for executing theinstructions to send the email message to the intended recipient thougha network 122. The network 122 can be the same or similar network as thenetwork 118 and network 120. For example, each network could be theInternet. In another implementation, the networks 118, 120, and 122 canbe different or can have some small degree of overlap.

The email client 144 can have a user interface 149 through which theuser 150 can view the sent message and through which the user can reviewthe status of the sent message in the email client 144. For example,after the email object is unpacked and the message is created within theOutbox of the email client, with the email user interface 149 the user150 can verify that the message has been created in the Outbox, andafter the message has been sent the user can see the message in the SentItems folder of the UI 149. After the scripting language code has beenexecuted and the email message has been sent from the mail server 140,control is returned again to the hosted application 104, and the user150 can perform the next action or task within the hosted application104.

In other implementation, when the email message is sent from the mailserver 140 it may bypass the email client application. For example, whenexecuted the scripting language code may cause the processor 136 tounpack the XML email object received from the server 102 and to send theemail message from the client to the SMTP server of the MicrosoftExchange Server running on the mail server 140. In this case, the SMTPcredentials of the mail server 140 must be identified to the client 130,so that the client can communicate directly with the mail server 140.

FIG. 2 illustrates screen shots of an exemplary e-mail user interface138 provided by the hosted application 104 running on the server 102 anda user interface 149 provided by an e-mail application 144 running onthe client 130. Within a body portion 202 of the interface 138 of thehosted application 104 the user 150 can compose the text of an emailmessage. Within a header portion 204 of the interface 138 the user canenter meta information about the email, such as the name and address orthe recipient, a subject of the email, the priority and sensitivity ofthe email message, and any files to be attached to the email. In arelations portion 206 of the interface 138 the user can relate the emailmessage to other data that is used in the hosted application. Forexample, the email can be related to one or more customer accounts orcontacts that are of interest to the user 150, and the relevance of theemail to a particular account or contact can be noted in a field of therelations portion 206. A control portion 208 of the interface 138 cancontain icons for performing various functions on the email, forexample, sending the email, sending the email and starting a new email,or cancelling the email.

After the user 150 has composed the email in the interface 138 andclicked an icon in the interface to send the email, then, as explainedabove, the data input by the user in the various portions 202, 204, 206,and 208 of the email user interface 138 is forwarded from the client 130to the server 102, where the email object engine 105 creates an emailobject that it sends back to the client 130, so that the client can sendthe email message from its own domain. After the email object receivedfrom the server 102 is unpacked on the client 130 and converted into anemail message, the email message can be loaded into the email clientapplication 144, where it is viewable in the UI 149 of the application144. The UI 144 can have several portions, including an individualmessage portion 210, an individual folder portion 212, and an overviewportion 214. Within the individual message portion 210, the emailmessage composed by the user 150 is displayed. The message portion 210can present to the user the body of the email 216, a signature block218, and a default letterhead block 220. The default letterhead andsignature blocks can be added automatically based on pre-stored data,either by the email client application 149 or by the email service ofthe hosted application 104. A header portion 222 within the individualmessage portion 210 can provide information about the subject, thesender, and the recipient of the email. The individual folder portion212 of the UI 149 can provide information about the individual messagescontained within a particular folder of the email client application144. For example, as shown in FIG. 2, the individual folder portion 212can show that the email message presented in portion 210 is a messagethat is stored in the Outbox folder of the application and that it wasstored in the Outbox folder at 3:05 pm on the day the user is viewingthe UI 149. The overview portion 214 presents overview information aboutall the user's email folders, including the user's favorite folders. Forexample, as shown in FIG. 2, when the label for the Outbox folder ispresented in bold font, the user would know that at least one unreviewedor unprocessed message is stored in the Outbox folder of the application140. The numeral “1” in parentheses after the name of the Outbox folderwould indicate to the user that only one unreviewed or unprocessedmessage is stored in the Outbox folder of the application 140. After amessage in the Outbox has been processed and sent, it may be moved tothe Sent Items folder of the application 140.

FIG. 3 is a flowchart illustrating an example method 300 of operatingthe system of FIGS. 1 and 2. IN a first step 302, the method begins withe-mail input data being received from a client at a server that isconfigured to serve a hosted application. The hosted applicationincludes an e-mail user interface that is served to the client, and thee-mail input data is used to generate an e-mail message from a user ofthe client to the recipient. The client is associated with a firstdomain, and where the server is associated with a second domain. Thee-mail input data can be composed within the e-mail user interface ofthe hosted application that is served to the client.

In a next step 304, an e-mail object is generated at the server, wherethe email object corresponds to the e-mail message from the user of theclient. Generating the e-mail object can include creating an XMLrepresentation of the e-mail message from the user of the client. Then,in a step 306, the e-mail object is forwarded from the server to theclient along with instructions to convert the e-mail object into thee-mail message and to send the e-mail message from the first domain. Itis also possible that at step 308 a copy of the e-mail message isgenerated at the server and stored in a storage device on the server forpresentation to the user through the e-mail user interface of the hostedapplication served to the client. Forwarding the e-mail object from theserver to the client can include sending instructions (e.g., in a Javascript) to the client to convert the e-mail object into the e-mailmessage and to send the e-mail message through a local e-mail clientapplication (e.g., Microsoft Outlook or Lotus Notes) associated with thefirst domain and configured to run on the client.

FIG. 4 is a flowchart illustrating an example method 400 of operatingthe systems of FIGS. 1 and 2. In a first step 402, an application hostedby a server and served to a client is accessed. The client is associatedwith a first domain and the server is associated with a second domain.The application includes an e-mail user interface that is served to theclient and runs on the client. In a next step 404, e-mail input data isreceived from a user of the client, and the e-mail input data is used togenerate an e-mail message from the user. The e-mail input data iscomposed within the e-mail user interface of a hosted application. Instep 406, e-mail input data is sent from the client to the server, andin step 408 an e-mail object corresponding to the e-mail message isreceived from the server. Then, the e-mail object is converted into thee-mail message (step 410), and the e-mail message is sent from the firstdomain (step 412).

Implementations of the various techniques described herein may beimplemented in digital electronic circuitry, or in computer hardware,firmware, software, or in combinations of them. Implementations may beimplemented as a computer program product, i.e., a computer programtangibly embodied in an information carrier, e.g., in a machine-readablestorage device or in a propagated signal, for execution by, or tocontrol the operation of, data processing apparatus, e.g., aprogrammable processor, a computer, or multiple computers. A computerprogram, such as the computer program(s) described above, can be writtenin any form of programming language, including compiled or interpretedlanguages, and can be deployed in any form, including as a stand-aloneprogram or as a module, component, subroutine, or other unit suitablefor use in a computing environment. A computer program can be deployedto be executed on one computer or on multiple computers at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

Method steps may be performed by one or more programmable processorsexecuting a computer program to perform functions by operating on inputdata and generating output. Method steps also may be performed by, andan apparatus may be implemented as, special purpose logic circuitry,e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. Elements of a computer may include atleast one processor for executing instructions and one or more memorydevices for storing instructions and data. Generally, a computer alsomay include, or be operatively coupled to receive data from or transferdata to, or both, one or more mass storage devices for storing data,e.g., magnetic, magneto-optical disks, or optical disks. Informationcarriers suitable for embodying computer program instructions and datainclude all forms of non-volatile memory, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks, e.g., internal hard disks or removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor andthe memory may be supplemented by, or incorporated in special purposelogic circuitry.

To provide for interaction with a user, implementations may beimplemented on a computer having a display device, e.g., a cathode raytube (CRT) or liquid crystal display (LCD) monitor, for displayinginformation to the user and a keyboard and a pointing device, e.g., amouse or a trackball, by which the user can provide input to thecomputer. Other kinds of devices can be used to provide for interactionwith a user as well; for example, feedback provided to the user can beany form of sensory feedback, e.g., visual feedback, auditory feedback,or tactile feedback; and input from the user can be received in anyform, including acoustic, speech, or tactile input.

Implementations may be implemented in a computing system that includes aback-end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront-end component, e.g., a client computer having a graphical userinterface or a Web browser through which a user can interact with animplementation, or any combination of such back-end, middleware, orfront-end components. Components may be interconnected by any form ormedium of digital data communication, e.g., a communication network.Examples of communication networks include a local area network (LAN)and a wide area network (WAN), e.g., the Internet.

While certain features of the described implementations have beenillustrated as described herein, many modifications, substitutions,changes and equivalents will now occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the embodiments.

1. A method comprising: receiving e-mail input data from a client at aserver that is configured to serve a hosted application that includes ane-mail user interface to the client, wherein the e-mail input data isused to generate an e-mail message from a user of the client, whereinthe client is associated with a first domain and the server isassociated with a second domain; generating, at the server, an e-mailobject corresponding to the e-mail message from the user of the client;and forwarding the e-mail object from the server to the client alongwith instructions to convert the e-mail object into the e-mail messageand to send the e-mail message from the first domain.
 2. The method ofclaim 1, wherein the e-mail input data is composed with the e-mail userinterface of the hosted application that is served to the client.
 3. Themethod of claim 1, wherein generating the e-mail object comprisescreating an XML representation of the e-mail message from the user ofthe client.
 4. The method of claim 1, wherein forwarding the e-mailobject from the server to the client comprises sending instructions tothe client to convert the e-mail object into the e-mail message and tosend the e-mail message through a local e-mail client applicationassociated with the first domain and configured to run on the client. 5.The method of claim 4, wherein the local e-mail client application isselected from the group consisting of Microsoft Outlook and Lotus Notes.6. The method of claim 4, wherein the data indicating that the clientshould unpack the e-mail object and send the e-mail message through alocal e-mail client application comprises a scripting language program.7. The method of claim 1, further comprising: generating a copy of thee-mail message at the server and storing the copy in a storage device onthe server for presentation to the user through the e-mail userinterface of the hosted application served to the client.
 8. A methodcomprising: accessing an application hosted by a server and served to aclient, wherein the application includes an e-mail user interface thatis served to the client and runs on the client, wherein the client isassociated with a first domain and the server is associated with asecond domain; receiving e-mail input data from a user of the client,wherein the e-mail input data is used to generate an e-mail message fromthe user and wherein the e-mail input data is composed within the e-mailuser interface of a hosted application; sending the e-mail input datafrom the client to the server; receiving from the server an e-mailobject corresponding to the e-mail message; converting the e-mail objectinto the e-mail message; and sending the e-mail message from the firstdomain.
 9. The method of claim 8, wherein receiving the e-mail objectcomprises receiving an XML representation of the e-mail message from theuser of the client.
 10. The method of claim 8, wherein sending thee-mail message comprises sending the message through a local e-mailclient application associated with the first domain and configured torun on the client.
 11. The method of claim 10, wherein the local e-mailclient application is selected from the group consisting of MicrosoftOutlook and Lotus Notes.
 12. The method of claim 8, further comprisingproviding the e-mail user interface of the application to the userthrough a browser application running on the client.
 13. The method ofclaim 8, further comprising: sending a confirmation message from theclient to server to inform the server that the e-mail message has beensent.
 14. A server system comprising: a network interface configured forconnecting the server system to a client system, wherein the client isassociated with a first domain and the server is associated with asecond domain; a processor configured for providing a hosted applicationthat is served to the client, wherein the hosted application includes ane-mail user interface within which a user of the client system cangenerate e-mail input data for sending an e-mail message from the user;an e-mail object generating engine adapted for receiving the e-mailinput data from the client and generating an e-mail object to be sent tothe client system along with instructions for converting the e-mailobject into an e-mail message to be sent from the first domain.
 15. Theserver system of claim 14, wherein the e-mail object comprises an XMLrepresentation of the e-mail message from the user of the client. 16.The server system of claim 14, wherein the instructions for convertingthe e-mail object into an e-mail message to be sent from the firstdomain include instructions to the client to send the e-mail messagethrough a local e-mail client application associated with the firstdomain and configured to run on the client.
 17. The server system ofclaim 16, wherein the local e-mail client application is selected fromthe group consisting of Microsoft Outlook and Lotus Notes.
 18. Theserver system of claim 16, wherein the instructions for converting thee-mail object into an e-mail message to be sent from the first domaincomprise a scripting language program.
 19. The server system of claim14, wherein the hosted application is a customer relations managementapplication.
 20. The server system of claim 14, wherein InternetProtocol header information of the sent e-mail message is associatedwith the first domain.